[INFO] fetching crate duskphantom-backend 0.0.2...
[INFO] fixing duskphantom-backend-0.0.2 against try#622891a4e29178280638a6b63a8908bde2c0c854+cargoflags=-Zfix-edition=start=2015 for pr-157817-2
[INFO] extracting crate duskphantom-backend 0.0.2 into /workspace/builds/worker-1-tc1/source
[INFO] started tweaking crates.io crate duskphantom-backend 0.0.2
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate duskphantom-backend 0.0.2
[INFO] tweaked toml for crates.io crate duskphantom-backend 0.0.2 written to /workspace/builds/worker-1-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate duskphantom-backend 0.0.2 on toolchain 622891a4e29178280638a6b63a8908bde2c0c854
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 128 packages to latest compatible versions
[INFO] [stderr]       Adding criterion v0.3.6 (available: v0.8.2)
[INFO] [stderr]       Adding rand v0.8.6 (available: v0.10.1)
[INFO] [stderr]       Adding thiserror v1.0.69 (available: v2.0.18)
[INFO] [stderr]       Adding z3 v0.12.1 (available: v0.20.1)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-backend` (manifest) generated 1 warning
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded duskphantom-utils v0.0.1
[INFO] [stderr]   Downloaded z3 v0.12.1
[INFO] [stderr]   Downloaded llvm-sys v160.2.1
[INFO] [stderr]   Downloaded duskphantom-frontend v0.0.1
[INFO] [stderr]   Downloaded duskphantom-graph v0.0.2
[INFO] [stderr]   Downloaded llvm-ir v0.11.3
[INFO] [stderr]   Downloaded duskphantom-middle v0.0.1
[INFO] [stderr]   Downloaded clang-front-back v0.0.1
[INFO] [stderr]   Downloaded z3-sys v0.8.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:3a6becf2bc8dde7f3fa57ede90e4f284e72d296796fc446bbb1e2c7cc0530151" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a
[INFO] running `Command { std: "docker" "start" "efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=" "-e" "RUSTDOCFLAGS=" "-w" "/opt/rustwide/workdir" "--user" "0:0" "efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fix" "--allow-no-vcs" "--allow-dirty" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zfix-edition=start=2015", kill_on_drop: false }`
[INFO] [stderr] warning: Cargo.toml: only one of `license` or `license-file` is necessary
[INFO] [stderr] `license` should be used if the package license can be expressed with a standard SPDX expression.
[INFO] [stderr] `license-file` should be used if the package uses a non-standard license.
[INFO] [stderr] See https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields for more information.
[INFO] [stderr] warning: `duskphantom-backend` (manifest) generated 1 warning
[INFO] [stderr]     Checking typed-arena v2.0.2
[INFO] [stderr]    Compiling llvm-ir v0.11.3
[INFO] [stderr]    Compiling syn v2.0.118
[INFO] [stderr]    Compiling llvm-sys v160.2.1
[INFO] [stderr]     Checking ordered-float v4.6.0
[INFO] [stderr]     Checking console v0.16.3
[INFO] [stderr]     Checking winnow v0.6.26
[INFO] [stderr]     Checking rayon v1.12.0
[INFO] [stderr]     Checking itertools v0.10.5
[INFO] [stderr]     Checking rustc-hash v2.1.2
[INFO] [stderr]     Checking duskphantom-graph v0.0.2
[INFO] [stderr]     Checking duskphantom-utils v0.0.1
[INFO] [stderr]     Checking insta v1.48.0
[INFO] [stderr]     Checking criterion-plot v0.4.5
[INFO] [stderr]    Compiling serde_derive v1.0.228
[INFO] [stderr]    Compiling thiserror-impl v1.0.69
[INFO] [stderr]     Checking thiserror v1.0.69
[INFO] [stderr]     Checking duskphantom-frontend v0.0.1
[INFO] [stderr]     Checking serde v1.0.228
[INFO] [stderr]     Checking serde_yaml v0.9.34+deprecated
[INFO] [stderr]     Checking tinytemplate v1.2.1
[INFO] [stderr]     Checking serde_cbor v0.11.2
[INFO] [stderr]     Checking criterion v0.3.6
[INFO] [stderr]     Checking clang-front-back v0.0.1
[INFO] [stderr]     Checking duskphantom-middle v0.0.1
[INFO] [stderr]     Checking duskphantom-backend v0.0.2 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:33:9
[INFO] [stdout]    |
[INFO] [stdout] 33 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep.to_string());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:39:9
[INFO] [stdout]    |
[INFO] [stdout] 39 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare base:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:44:9
[INFO] [stdout]    |
[INFO] [stdout] 44 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare offset:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:52:9
[INFO] [stdout]    |
[INFO] [stdout] 52 |         fprintln!("log/build_gep_inst.log";'a';"\ngen:\n{}\n",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:29:9
[INFO] [stdout]    |
[INFO] [stdout] 29 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:38:9
[INFO] [stdout]    |
[INFO] [stdout] 38 |         fprintln!("log/build_gep_inst.log";'a';"ofst:{:?}",ofst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:63:9
[INFO] [stdout]    |
[INFO] [stdout] 63 |         fprintln!("log/build_gep_inst.log";'a';"base:{:?}", base);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:68:9
[INFO] [stdout]    |
[INFO] [stdout] 68 |         fprintln!("log/build_gep_inst.log";'a';"final:{:?}", dst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `crate::*`
[INFO] [stdout]   --> src/from/from_self/vars.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 | use crate::*;
[INFO] [stdout]    |     ^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> src/from/from_self/mod.rs:30:9
[INFO] [stdout]    |
[INFO] [stdout] 30 | pub use instruction::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^ the name `block` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 34 | pub use super::irs::*;
[INFO] [stdout]    |         ------------- but the name `block` in the type namespace is also re-exported here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(ambiguous_glob_reexports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `checker::ProgramChecker`
[INFO] [stdout]   --> src/irs/prog.rs:17:5
[INFO] [stdout]    |
[INFO] [stdout] 17 | use checker::ProgramChecker;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:68:5
[INFO] [stdout]    |
[INFO] [stdout] 68 |     fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:71:9
[INFO] [stdout]    |
[INFO] [stdout] 71 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:82:5
[INFO] [stdout]    |
[INFO] [stdout] 82 |     fprintln!("log/before_inst_combine.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:92:5
[INFO] [stdout]    |
[INFO] [stdout] 92 |     fprintln!("log/after_inst_scheduling.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:95:5
[INFO] [stdout]    |
[INFO] [stdout] 95 |     fprintln!("log/after_reg_alloc.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:35:5
[INFO] [stdout]    |
[INFO] [stdout] 35 |     fprintln!("log/before_handle_unlegal_inst.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:41:5
[INFO] [stdout]    |
[INFO] [stdout] 41 |     fprintln!("log/before_phisicalize.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:45:5
[INFO] [stdout]    |
[INFO] [stdout] 45 |     fprintln!("log/phisicalize_func.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 |     fprintln!("log/handle_ra.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     fprintln!("log/handle_stack.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:65:5
[INFO] [stdout]    |
[INFO] [stdout] 65 |     fprintln!("log/handle_mem.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:69:5
[INFO] [stdout]    |
[INFO] [stdout] 69 |     fprintln!("log/handle_offset_overflows.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:33:9
[INFO] [stdout]    |
[INFO] [stdout] 33 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep.to_string());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:39:9
[INFO] [stdout]    |
[INFO] [stdout] 39 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare base:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:44:9
[INFO] [stdout]    |
[INFO] [stdout] 44 |         fprintln!("log/build_gep_inst.log";'a';"\nafter prepare offset:\n{}",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_llvm/build_inst/gep.rs:52:9
[INFO] [stdout]    |
[INFO] [stdout] 52 |         fprintln!("log/build_gep_inst.log";'a';"\ngen:\n{}\n",asm_of_insts(&ret));
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:29:9
[INFO] [stdout]    |
[INFO] [stdout] 29 |         fprintln!("log/build_gep_inst.log";'a';"gep:{}",gep);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:38:9
[INFO] [stdout]    |
[INFO] [stdout] 38 |         fprintln!("log/build_gep_inst.log";'a';"ofst:{:?}",ofst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:63:9
[INFO] [stdout]    |
[INFO] [stdout] 63 |         fprintln!("log/build_gep_inst.log";'a';"base:{:?}", base);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/from/from_self/instruction/gep.rs:68:9
[INFO] [stdout]    |
[INFO] [stdout] 68 |         fprintln!("log/build_gep_inst.log";'a';"final:{:?}", dst);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `crate::*`
[INFO] [stdout]   --> src/from/from_self/vars.rs:24:5
[INFO] [stdout]    |
[INFO] [stdout] 24 | use crate::*;
[INFO] [stdout]    |     ^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: ambiguous glob re-exports
[INFO] [stdout]   --> src/from/from_self/mod.rs:30:9
[INFO] [stdout]    |
[INFO] [stdout] 30 | pub use instruction::*;
[INFO] [stdout]    |         ^^^^^^^^^^^^^^ the name `block` in the type namespace is first re-exported here
[INFO] [stdout] ...
[INFO] [stdout] 34 | pub use super::irs::*;
[INFO] [stdout]    |         ------------- but the name `block` in the type namespace is also re-exported here
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(ambiguous_glob_reexports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `checker::ProgramChecker`
[INFO] [stdout]   --> src/irs/prog.rs:17:5
[INFO] [stdout]    |
[INFO] [stdout] 17 | use checker::ProgramChecker;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:68:5
[INFO] [stdout]    |
[INFO] [stdout] 68 |     fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:71:9
[INFO] [stdout]    |
[INFO] [stdout] 71 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         fprintln!("2.s", "{}", func.gen_asm());
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:82:5
[INFO] [stdout]    |
[INFO] [stdout] 82 |     fprintln!("log/before_inst_combine.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:92:5
[INFO] [stdout]    |
[INFO] [stdout] 92 |     fprintln!("log/after_inst_scheduling.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/optimize/mod.rs:95:5
[INFO] [stdout]    |
[INFO] [stdout] 95 |     fprintln!("log/after_reg_alloc.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:35:5
[INFO] [stdout]    |
[INFO] [stdout] 35 |     fprintln!("log/before_handle_unlegal_inst.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:41:5
[INFO] [stdout]    |
[INFO] [stdout] 41 |     fprintln!("log/before_phisicalize.log", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:45:5
[INFO] [stdout]    |
[INFO] [stdout] 45 |     fprintln!("log/phisicalize_func.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 |     fprintln!("log/handle_ra.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     fprintln!("log/handle_stack.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:65:5
[INFO] [stdout]    |
[INFO] [stdout] 65 |     fprintln!("log/handle_mem.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `log_enabled`
[INFO] [stdout]   --> src/phisicalize.rs:69:5
[INFO] [stdout]    |
[INFO] [stdout] 69 |     fprintln!("log/handle_offset_overflows.s", "{}", func.gen_asm());
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `backend_opt`, `clang_enabled`, `default`, `gen_virtual_asm`, `ilp_alloc`, `llvm-ir`, `opt_address_computation`, and `z3`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `fprintln` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `fprintln` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/irs/func.rs:155:21
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter {
[INFO] [stdout]     |                     ^^^^^     ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter<'_> {
[INFO] [stdout]     |                                     ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/optimize/analysis/cfg.rs:100:26
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs, OutBBs)> {
[INFO] [stdout]     |                          ^^^^^             ^^^^^  ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                          |                 |
[INFO] [stdout]     |                          |                 the same lifetime is hidden here
[INFO] [stdout]     |                          the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs<'_>, OutBBs<'_>)> {
[INFO] [stdout]     |                                                 ++++        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/irs/func.rs:155:21
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter {
[INFO] [stdout]     |                     ^^^^^     ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                     |
[INFO] [stdout]     |                     the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 155 |     pub fn iter_bbs(&self) -> BBIter<'_> {
[INFO] [stdout]     |                                     ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/optimize/analysis/cfg.rs:100:26
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs, OutBBs)> {
[INFO] [stdout]     |                          ^^^^^             ^^^^^  ^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                          |                 |
[INFO] [stdout]     |                          |                 the same lifetime is hidden here
[INFO] [stdout]     |                          the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 100 |     pub fn in_out_bbs(f: &Func) -> Result<(InBBs<'_>, OutBBs<'_>)> {
[INFO] [stdout]     |                                                 ++++        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 20.64s
[INFO] [stderr] crater-edition-check: all finished
[INFO] running `Command { std: "docker" "inspect" "efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a", kill_on_drop: false }`
[INFO] [stdout] efef436970716a60698fac6b2ddbdf281153ad58a33ed8e9d124a5e1229c8f4a
